ci: migrate release automation to release-please#2
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Migrate release automation from the tag-driven git-cliff workflow to release-please.
Added
.github/workflows/release-please.yml— runs on push tomain.release-please-config.json— single package.,release-type: python(owns the version directly inpyproject.toml),bump-minor-pre-majorfor the0.xline..release-please-manifest.json— seeded with the current released version0.2.0.Removed
.github/workflows/release.yml(git-cliff, tag-driven) andcliff.toml.Updated
pyproject.toml—[tool.commitizen]scoped to commit-msg validation only.README.mdanddocs/WORKFLOW.md— document the new release flow.New release flow
Land Conventional Commits on
main→ release-please opens/maintains a release PR with the bump + changelog → merge it → tagvX.Y.Z+ GitHub Release.Manual step required on merge
Settings → Actions → General → Workflow permissions → enable "Read and write permissions" and "Allow GitHub Actions to create and approve pull requests" — otherwise the action can't open the release PR.
Notes
Stacked on #1 — base is
feat/quality-tooling. GitHub will retarget this tomainautomatically once #1 merges, leaving a migration-only diff.